I've just received a notification that this issue has been addressed in Xcode 26.3, which introduced a setting to enable individual width for navigators/inspectors in window tabs. It's great that the Xcode team listens to our feedback.

@DTS Engineer: Thanks for chiming in, Ed. I've just received a notification that this issue has been addressed in Xcode 26.3, which introduced a setting to enable individual width for navigators/inspectors in window tabs. It's great that the Xcode team listens to our feedback. P.S. My next rant that I'm about to post will be regarding the bug FB19249805 to highlight another productivity downgrade in Xcode 26: the inability to open files in new window tabs, which destroys workflows that have been established for many years.

[quote='813773022, DTS Engineer, /thread/768383?answerId=813773022#813773022'] FB15529007 has definitely made it to right folks. [/quote] Yes! Fixed in Xcode 16.2 RC. Thanks for chiming in, Quinn.

[quote='813773022, DTS Engineer, /thread/768383?answerId=813773022#813773022'] FB15529007 has definitely made it to right folks [/quote] ok that's good to know, thanks!

[quote='813572022, DTS Engineer, /thread/768383?answerId=813572022#813572022'] Please post the bug number of the bug that you filed. [/quote] FB15529007 Thanks!

Astonishingly, this severe bug is still not fixed in Xcode 16. Once again, this bug affects EVERY XCODE USER. I'm truly curious why Apple refuses to fix this basic Info.plist management bug? Especially that this one is trivial to fix. Up until Xcode 14, Xcode functioned normally. Now such basic things as specifying the build version or app category cannot be performed by just typing or selecting the desired values. Is Apple waiting for quantum computers and next generation AI technologies to restore some basic functionality of plist management? What kind of super-human developers worked in Xcode team until version 14 that they were able to provide basic UI updates from NSDictionary? I guess those ultra-ingenious developers have left and took the sacred secrets of reading an NSDictionary with them forever :(

And here we are: still NONE of the issues are fixed in Xcode 15 beta 4. Once again, some of them (such as build number mismatch) affects ALL Xcode users - 100% of them. It's unfathomable how Apple managed to break Info.plist management in Xcode 14 (something that worked with no issues since the first Xcode release). It's even harder to understand why they still refuse to fix it while, once again, this affects ALL Xcode users. I encourage every Xcode user to submit a bug report regarding this severe problem as soon as possible. Maybe Apple pays attention to this once they receive a few hundred reports on this bug.

I just had a similar issue today. Couldn't notarize anything for couple hours — notarization just took forever. Just had another attempt — and notarization this time succeeded after some 10 minutes. I assume notarization servers were broken today for some time. I doesn't explain, of course, the issues you had on other days.

This comment is added on Apple's request to test a forum notification bug. Sorry!

...and none of this is fixed in the Xcode 15.0 release. The first bug (Build value) affects EVERY Xcode user. I find it astonishing that Apple refuses to address such glaring deficiencies in fundamental Xcode functionality. Especially something that should be trivial to fix.

@mgrushin: Thanks!! It did work. I'm still not sure what it's all about... Mac apps don't require any provisioning profiles. I don't have any provisioning profiles specified. But now I see that indeed a provisioning profile is generated in ~/Library/MobileDevice/Provisioning Profiles upon submission of the app to Mac App Store. The directory is also named MobileDevice while, once again, it's not a mobile app - but I guess that's how it works. Thanks again! Leo

no. yes.

to answer your subject question: NO

Yes, I have an app that's using SMTP services in Mac App Store.

I can confirm that Info.plist management is totally screwed in Xcode 14. While I didn't seem to have issues in the Target Properties section, the Document Types section is simply dysfunctional. I submitted bugs to Apple.